fix: forced assignment redemption assigns course run key #570
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Currently, the forced redemption model persists a course run key to force redeem. It also creates an assignment if in an assignment-based policy. However, it creates the assignment with a course key, and not the run key.
Instead of doing this, we should simply fetch the metadata for the course run key that’s persisted in the forced redemption instance. As long as we get something back, we should just use this persisted value when creating the related assignment record.
Jira:
https://2u-internal.atlassian.net/browse/ENT-9562
Merge checklist:
./manage.py makemigrations
has been runPost merge: